Skip to content

smartart:0.1.0#5178

Open
CRAG666 wants to merge 3 commits into
typst:mainfrom
CRAG666:main
Open

smartart:0.1.0#5178
CRAG666 wants to merge 3 commits into
typst:mainfrom
CRAG666:main

Conversation

@CRAG666

@CRAG666 CRAG666 commented Jun 27, 2026

Copy link
Copy Markdown

SmartArt-style diagram widgets for posters and presentations.

Widgets included:
card-table, gantt, process, pyramid, hierarchy, steps, venn, hlist, chevron, cycle, target, matrix, snake, stairs, gears, timeline, tree, arrows (converging/diverging), opposing, equation, kpi, pill-steps

Each widget renders colorful, presentation-ready diagrams with customizable colors, sizes, and layouts. The README includes usage examples and screenshots for every widget.

@CRAG666 CRAG666 temporarily deployed to Package Check June 27, 2026 04:45 — with GitHub Actions Inactive
@typst-package-check typst-package-check Bot changed the title Add smartart v0.1.0 — SmartArt-style diagrams for Typst smartart:0.1.0 Jun 27, 2026
@typst-package-check typst-package-check Bot added the new A new package submission. label Jun 27, 2026
@CRAG666 CRAG666 temporarily deployed to Package Check June 27, 2026 04:51 — with GitHub Actions Inactive
@saecki

saecki commented Jun 30, 2026

Copy link
Copy Markdown
Member

Thanks for the package submission. Could you please fill in the checklist that is usually provided as a PR template. Especially the package name explanation.

<!--
Thanks for submitting a package! Please read and follow the submission guidelines detailed in the repository's README and check the boxes below. Please name your PR as `name:version` of the submitted package.

If you want to make a PR for something other than a package submission, just delete all this and make a plain PR.
-->

I am submitting
- [ ] a new package
- [ ] an update for a package

<!--
Please add a brief description of your package below and explain why you think it is useful to others. If this is an update, please briefly say what changed.
-->

Description: Explain what the package does and why it's useful.

<!--
These things need to be checked for a new submission to be merged. If you're just submitting an update, you can delete the following section.
-->

I have read and followed the submission guidelines and, in particular, I
- [ ] selected [a name](https://github.com/typst/packages/blob/main/docs/manifest.md#naming-rules) that isn't the most obvious or canonical name for what the package does
  - Explanation:
    <!--
    Please write one or two sentences explaining:
    1. the name of your package, if necessary, e.g:
      > Pergamon was an ancient Greek city state in Asia Minor. Its library was second only to the Library of Alexandria around 200 BC.
    2. why it isn't too canonical/descriptive and complies with the naming rules, e.g:
      - The name is a related but creative term
      - The name is a neologism combining the words … and …
      - The name contains a non-descriptive prefix
      - The package is official ⇒ an email will be sent to hello@typst.app
    -->
- [ ] added a [`typst.toml`](https://github.com/typst/packages/blob/main/docs/manifest.md#package-metadata) file with all required keys
- [ ] added a [`README.md`](https://github.com/typst/packages/blob/main/docs/documentation.md) with documentation for my package
- [ ] have chosen [a license](https://github.com/typst/packages/blob/main/docs/licensing.md) and added a `LICENSE` file or linked one in my `README.md`
- [ ] tested my package locally on my system and it worked
- [ ] [`exclude`d](https://github.com/typst/packages/blob/main/docs/tips.md#what-to-commit-what-to-exclude) PDFs or README images, if any, but not the LICENSE

<!--
The following box only needs to be checked for **template** submissions. If you're submitting a package that isn't a template, you can delete the following section. See the guidelines section about licenses in the README for more details.
-->
- [ ] ensured that my package is licensed such that users can use and distribute the contents of its template directory without restriction, after modifying them through normal use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new A new package submission.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants